Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The contour UI is disabled, and the storage of the contours in the pulse metadata is quite large and unnecessary. This adds a Django setting variable to enable contour calculation. By default, it is disabled and won't perform the contour calculation
DJANGO_BATAI_SAVE_SPECTROGRAM_CONTOURS- defaults to FALSE and when set to TRUE will perform contour calculations when a waveform is processed into the spectrograms.bbox is a required field for creating pulse metadata so I added some calculation from the basic segment data as well as a fallback from the curve for when the
DJANGO_BATAI_SAVE_SPECTROGRAM_CONTOURS=False